Release notes 2025

This page contains release notes that apply to all APIs on the Base platform for the 2025 versions.

2025r3

Fix for empty collections

Previously, sending POST or PUT calls using any of the BAPIs would crash if a collection array was empty, such as broadcastWindows in the POST /trailers call of the trailer API, and no corresponding message existed to signal that it could not be removed. This issue has been fixed in this version. The APIs can now handle empty collection arrays.

2025r1

Performance tracing on business API and open API

When the business API or open API services execute REST calls, they are logged in a REST exchange log entry. This log entry shows how long it took to receive a response.

To have more information on what is done during these calls, the performance tracing can also be enabled on the Business API interface service and Configurable REST interface service.

In the Logging tab, the PERFORMANCE TRACING group box has been added with the following properties:

• A note to inform users that the service has to be restarted after selecting the check box below.

• Allow performance tracing: Select to enable performance tracing for the service. When this is done, the Performance tracing threshold is enabled.

• Performance tracing threshold (seconds): Type or choose the threshold for the performance tracing, which is set to 60 seconds by default. The minimum value is 0, which can be used to trace calls that only take milliseconds. Performance tracing applies only to calls that exceed the defined threshold.

Note that the Logging check box in the tab also has to be selected or the performance is not traced either.

See the performance tracing browser and navigator for more info on the performance logs.